System and method for common file installation

ABSTRACT

The invention provides a method and system for creating a single, common installation file for multiple target device types. In one approach, the method comprises providing a base engine, compiling the engine into an intermediate language code, and just-in-time compiling the intermediate code into executable code. The latter code is executed to gather the appropriate data sets and concatenate the data sets with the engine to form the installation file. The present invention also provides a method and system for utilizing the installation file to retrieve the appropriate data set(s) for the identified target device type, and to install the retrieved data set(s) onto the target device.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to software installation and, moreparticularly, a system and method for creating and deploying a singlecommon software file that can be used to install the appropriate datasets on multiple devices having different processors or operatingsystems.

2. Description of Related Art

Different electronic devices (e.g., desktop computers, laptop computers,pocket personal computers, personal digital assistants, handheldcomputers, cell phones, etc.) can have different hardware and softwarecomponents with unique specifications and settings. For example,electronic devices can comprise numerous different operating systems andprocessor types. A device having a unique operating system-processorcombination typically needs a unique installation file in order to beable to install the proper files onto it. The need for device-specificinstallation files largely results from using native programminglanguages that require executables and supporting code files to becompiled for a specific processor type. Sometimes, the device-specificinstallation files contain code for the specific operating system.Currently, installing a set of files to devices with differentprocessors and/or operating systems requires a different type ofsoftware file for each unique processor-operating system combination.

Examples of existing programs that perform installation functionsinclude Wise Windows Installer, Wise for Visual Studio .NET,InstallShield's installation utility, Microsoft's CabWiz, andMicrosoft's Setup and Deployment Wizard in Visual Studio .NET 2003. Noneof these products comprise a single common file that can be deployed onmultiple platforms; rather, these products create and/or utilizenumerous different installation packages for differentprocessor/operating system combinations. FIG. 1 depicts a typicalcurrent software installation system 10 that comprises a developmentplatform or computer 12, a plurality of installation files (e.g., files14, 16, 18, 20, 22, and 24), a file deployment subsystem 26, and aplurality of target devices (e.g., devices 30, 32, 34, 36, 38, and 40).

With continued reference to FIG. 1, the development platform 12comprises a computer with processor W and operating system A. Each ofthe target devices comprises an operating system from a group consistingof A, B, and C, and a processor type from a group consisting of W, X, Y,and Z. Device 30 is a cell phone with operating system B and processorX. Device 32 is a personal digital assistant (PDA) that has processor Yand operating system B. Device 34 is a PDA with operating system C andprocessor Z. Device 36 is a PDA with operating system C and processor Y.Device 38 is a desktop computer with operating system A and processor W.Device 40 is a laptop computer with operating system B and processor W.

There is a different installation file for each of the devices.Specifically, installation file 14 is specific to a cell phone havingprocessor X and operating system B. Similarly, installation files 16,18, 20, 22, and 24 are geared toward devices 32, 34, 36, 38, and 40,respectively. File transportation system 26 comprises a medium, network,or the like, that facilitates the deployment of files 14, 16, 18, 20,22, and 24 to devices 30, 32, 34, 36, 38, and 40, respectively. Forexample, deployment subsystem 26 can comprise CDs, downloadable files,network connections, or the like, or combinations thereof.

A typical current software installation method comprises the steps ofrunning a program on a development computer 12 to create a uniqueinstallation file for each processor and operating system combination,deploying the installation files to the appropriate target devices, andcopying and running each unique install file on the respective targetdevice to perform the installation.

For a customer that uses various different types of devices, each withdifferent operating systems and/or processor types, it is inconvenient,time-consuming, and perhaps confusing if he/she has to install multipleversions of a given type of software onto his/her devices. For example,with reference to FIG. 1, a consumer may own three different types ofpersonal computers (PCs)—namely, a pocket PC 36, a desktop PC 38, and alaptop PC 40—wherein each PC has a unique processor-operating systemcombination. As a result, the consumer would have to download andinstall three different versions or types of an installation software(e.g., a new program, patch, virus definition list, or the like).

What is desired is a system and method for installing software or dataonto target devices with a single, common installation file, whichexpedites the process of loading the software/data onto multipledevices, and thereby saves customers time spent on figuring out whichinstallation file(s) is needed to install software/data to a specifictype of device.

SUMMARY OF THE INVENTION

The present invention provides a system and method for installing datafiles or digital information on multiple types of target devices using acommon installation file. While software programs that performinstallation functions have been adapted for different types ofelectronic device platforms, they have not heretofore been designed as asingle common file that can be deployed to and compiled on multipleplatforms.

In accordance with one aspect of the embodiments described herein, thereis provided a method of installing data onto a target device. In oneapproach, the method comprises providing an installation file, theinstallation file comprising an engine and plural data setscorresponding respectively to plural target device types, the enginebeing in an intermediate language code. The method further comprisesloading the installation file onto the target device and just-in-timecompiling the engine into code executable on the target device type. Thecompiled engine is executed to identify the target device as one of theplural target device types, to retrieve the corresponding one of theplural data sets for the identified target device type, and to installthe retrieved data set onto the target device.

In accordance with another aspect of the embodiments described herein,there is provided a method of creating an installation file. In oneapproach, the method comprises providing a base engine written in sourcecode and compiling the engine into an intermediate language code. Themethod further comprises just-in-time compiling the intermediatelanguage code of the engine into executable code. The compiled code isexecuted to gather plural data sets corresponding respectively to pluraltarget device types and concatenate the intermediate language code ofthe engine with the gathered data sets to form the installation file.

In accordance with yet another aspect of the embodiments describedherein, there is provided a computer program product that comprises anengine and plural data sets corresponding respectively to plural targetdevice types. In one embodiment, the engine of the product comprisescomputer executable instructions to be just-in-time compiled into codeexecutable on a target device. The target device executable codepreferably comprises instructions for retrieving the corresponding oneof the plural data sets for the identified target device type, andinstalling the retrieved plural data set onto the target device.

A more complete understanding of the software installation system andmethod described herein will be afforded to those skilled in the art, aswell as a realization of additional advantages and objects thereof, by aconsideration of the following detailed description of the preferredembodiment. Reference will be made to the appended sheets of drawingswhich will first be described briefly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram illustrating a prior art softwareinstallation system that comprises different installation files that aredeployed to the various different devices.

FIG. 2 is a system diagram illustrating an embodiment of a softwareinstallation system that utilizes a single common installation file thatis deployed to the various different types of devices.

FIG. 3 is a block diagram showing the relationship between the softwareused to build the installation file and the installation file that isdeployed to the target computing devices.

FIG. 4 is a flowchart illustrating a method of creating and deploying asingle common installation file to one or more target devices types inaccordance with an embodiment of the present invention.

FIG. 5 is a block diagram showing the relationship between the sourcecode of the installation file and the code that is executed by thetarget device.

FIG. 6A is a block diagram showing a base engine and plural data filesthat exist as separate files before the installation file is created.

FIG. 6B is a block diagram showing the base engine and plural data filesof FIG. 6A concatenated into a single installation file.

FIG. 6C is a block diagram showing the engine portion of theinstallation file in FIG. 6B being just-in-time compiled on the targetdevice, allowing the data files to be extracted onto the target device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention satisfies the need for a file installation systemand method that involves creating, deploying, and using a singlesoftware file to install the appropriate files on different types ofdevices. In the detailed description that follows, like element numeralsare used to describe like elements illustrated in one or more of thefigures.

In accordance with one aspect of the embodiments described herein, thereis provided a file installation system that comprises a developmentcomputer for creating an installation file, and a subsystem fordeploying the installation file from the development computer to aplurality of target devices. Each target device typically receives andruns the installation file to extract the appropriate file set(s) fromthe installation file based on the specifications of the target device(e.g., operating system, processor type, etc.), wherein the file set(s)comprises data to be installed on the target device.

In one exemplary embodiment, illustrated in FIG. 2, the installationfile system 50 generally comprises a development computer 12 used tocreate an installation file 52, and a file deployment subsystem 54 fordeploying the installation file 52 to a plurality of target devices(e.g., devices 30, 32, 34, 36, 38, and 40). As with system 10 in FIG. 1,system 50 comprises a plurality of target devices wherein each of thedevices has an operating system from a group consisting of A, B, and C,and a processor from a group consisting of W, X, Y, and Z. In contrastto system 10 of FIG. 1, however, system 50 does not require a differentinstallation file for each of the devices; rather, system 50 comprises asingle common installation file 52 that is compatible with targetdevices 30, 32, 34, 36, 38, and 40. In one embodiment, the installationfile 52 comprises a concatenated package of file sets wherein a subsetof the file sets are extracted and installed on any given target device,as explained in further detail below. In another embodiment, theinstallation file 52 comprises a concatenated package of data sets inlieu of file sets.

The file deployment subsystem 54 comprises any suitable medium, network,or the like that facilitates the deployment of installation file 52 ontodevices 30, 32, 34, 36, 38, and 40. For example, in one embodiment,subsystem 54 comprises a personal computer, an internet connection, amodem for interfacing the PC with the internet, and a cradle orconnector for connecting the target device (e.g., a personal digitalassistant, cell phone, etc.) with the PC. An installation file 52 can bedownloaded from the internet onto the PC and then transferred to one ormore connected target devices. In another embodiment, the subsystem 54comprises a PC, a storage medium (e.g., a compact disc) that containsthe installation file 52, and a connector for the target device. Theinstallation file 52 can be saved to the PC, which in turn transfers theinstallation file 52 to one or more target devices. In anotherembodiment, where the target device is a desktop computer 38 or laptopcomputer 40, the subsystem 54 comprises an internet connection and amodem for interfacing the target device with the internet, so that theinstallation file 52 can be downloaded directly onto the target device(e.g., computer 38 or 40).

The exemplary development platform or computer 12 shown in FIG. 2 is notmeant to indicate that only one type of machine can be used to createthe installation file 52. Also, the types of target devices (e.g.,devices 30 and 38) shown in FIG. 2 are only a small subset of thecomputing and electronics devices that can receive and utilize aninstallation file 52 received over deployment subsystem 54. It will beunderstood that the file installation method and system disclosed hereincan be used to install any type of file on any target computing devicewith memory, and is not limited to traditional computing devices orspecific types of files.

In accordance with another aspect of the embodiments described herein,there is provided a method of creating an installation file. Withreference to FIG. 3, the installation file is typically created on adevelopment computer 12 by running a installation file developmentprogram 13, which comprises a base engine written in source code. Forexample, the base engine can be programmed in C# on the developmentcomputer 12. Alternatively, the engine can be programmed in Visual Basic.NET or another similar programming language. The base engine iscompiled into an intermediate language code on the development computer12. For example, a stage compiler (e.g., Java compiler, .NET compiler,or the like) can be used to compile the base engine from source code toan agnostic, intermediate language code, which can be just-in-timecompiled on the development computer 12, as shown in FIG. 5. When theintermediate language code of the engine is just-in-time compiled intocode executable on the development computer 12, the computer 12 executesthe compiled code to create the installation file. The specifics of howthe executed code generates the installation file is explained infurther detail below.

The installation file preferably comprises the engine, which is inintermediate language code, and one or more data sets that are to beinstalled on one or more target devices. FIG. 6A illustrates a baseengine 100 and data files 1 through n (e.g., 102, 104, 106, and 108) asseparate files before the engine the installation file 52 is created.The engine 100 is in intermediate language code if it has been compiledby a compiler, such as a .NET compiler, on the development platform 12;otherwise, the engine 100 remains in source code.

FIG. 6B shows the installation file 52 that results when the engine 100in intermediate language code is just-in-time compiled into machineexecutable code. In a preferred approach, the engine 100 is just-in-timecompiled on the development platform 12 into code that is executable bythe development platform. The development platform executes the compiledcode to gather plural files (e.g., files 1 through n) correspondingrespectively to plural target device types and concatenate the engine100 with the gathered files 1 through n, thereby generating installationfile 52. In an alternative approach, the engine 100 is just-in-timecompiled on a machine other than the development platform 12. Still, themachine executes the compiled engine code to create the installationfile 52 by gathering data files 1 through n and concatenating thesefiles with the engine 100. The engine 100 and data files 1 through n areconcatenated to form a single, common installation file 52 that can beused to install the appropriate data (e.g., 102, 104, 106, and 108) onthe target device (e.g., device 30), as illustrated in FIG. 6C. Theinstallation of the data files on the target device(s) is explained infurther detail below.

With reference to FIGS. 3 and 6B, once the just-in-time compiled enginecode is executed on the development computer 12, the computer 12 gathersthe plural data sets corresponding respectively to the plural targetdevice types (e.g., devices 30, 32, 34, 36, 38, and 40) and concatenatesthe intermediate language code of the engine with the gathered data setsto form the installation file. In an alternative approach, the computer12 gathers plural file sets corresponding respectively to the pluraltarget device types and concatenates the intermediate language code ofthe engine with the gathered file sets to form the installation file 52.

The computer 12 can gather the plural data/file sets in any number ofways. In one approach, the computer 12 queries the user for informationregarding the target device(s) during the installation file creationprocess, as shown in step 68 of FIG. 4. For example, in one approach,the program 13 on computer 12 queries the user for the list of targetdevices, types of processors and operating systems are on the targetdevices, etc. in order to build an installation file that is compatiblewith each of the target devices. Other factors that can be consideredwhen building the installation file include: which data/files are neededto go into the installation file, where to extract the data/files towhen they are installed; the dynamic root entry, and any otherinformation that facilitates dynamically installing the data/files ontothe target devices. Because different devices can have differentdirectory structures, the dynamic root information allows for theappropriate data/files to be extracted to appropriate paths based on thetype of target device on which installation is being performed. The userentered data can also include information relating to what to call thenew installation file and the coding format of the installation file.

Alternatively, the program 13 obtains information regarding the targetdevice(s) from another file on the computer 12, the system settings,and/or registry. For example, in one scenario where one or more of thetarget devices are or have been connected to the computer 12, theprogram 13 checks the registry to determine the types of devices thathave been connected to computer 12, whether or not programs such asActiveSync or the like are available. In a preferred approach, theprogram 13 accesses another file on the computer 12 that has a list ofthe data files that need to be installed onto the target devices.Certain of the methods described herein are refer to the gathering andinstallation of data files to target devices. It will be understood,however, that the same or similar methods can be used to install data(not in file form) on the target devices, either in lieu of or inconjunction with data files. In one approach (not illustrated), one ormore of the data files to be installed on the target devices areencrypted and/or compressed.

The methods and embodiments explained herein describe the aninstallation file that comprises the base engine in intermediatelanguage code and plural data sets for the plural target device types.It will be understood, however, that in another approach, the pluraldata sets are concatenated with a separate set of instructions inintermediate language code, either in lieu of or in conjunction with thebase engine. For example, instead of attaching the plural data sets tothe same engine that was used to query information from the developer,data sets are attached to another smaller engine capable of extractingthe data sets from the installation file, thereby resulting in a smallerinstallation file. In another approach, part of the dynamic informationobtained from the user is used to determine which subset of files toextract from the installation file 52. With the ubiquity of .NET, (anapplication development platform), Java, and other platform agnosticdevelopment environments and with the promise of portable code, oneskilled in the art will recognize that there are numerous approaches todesigning file installation systems and components that allow the samefile to be installed on different types of devices that can havedifferent operating systems and/or types of processors.

In accordance with yet another aspect of the embodiments describedherein, there is provided a method of installing data onto a targetdevice. In a preferred approach, the method involves deploying a singlecommon installation file that is run on all target devices, therebyeliminating the need to create and deploy multiple installation filesfor multiple devices. The method generally comprises deploying aninstallation file to one or more target devices, and extracting theappropriate files from the installation file onto the target devices. Inan exemplary approach, the method further comprises the step ofcollecting information from a user to build the installation/deploymentfile.

For example, with reference to FIGS. 2 and 3, in one approach toinstalling files to multiple target devices with a single installationfile comprises the steps of: (1) running a program 13 on a developmentplatform 12 to create an installation file 52; (2) deploying theinstallation file 52 to one or more targeted devices; and (3) runningthe installation file 52 on each target device (e.g., devices 30, 32,34, 36, 38, and 40). The installation file 52 is deployed to the targetdevices via any suitable file transfer medium. For example, the step ofdeploying the installation file can comprise placing the installationfile 52 on a remote file system that is accessible by the plural targetdevice types, so that the installation file can be downloaded onto thetarget device types. In one approach, the installation file is uploadedto an internal network system. In another approach, the installationfile is uploaded to an internet site. Alternatively, the step ofdeploying or providing the installation file can comprise saving theinstallation file onto a storage medium (e.g., a compact disc) anddistributing the storage medium to users of the plural target devicetypes, so that the users can load the installation file onto the theirrespective target devices.

In a preferred approach, the method of installing data onto a targetdevice comprises providing an installation file that comprises an engineand plural data sets corresponding respectively to plural target devicetypes. As explained above, the engine is in an intermediate languagecode. The method further comprises loading the installation file ontothe target device and just-in-time compiling the engine into codeexecutable on the target device type. Next, target device executablecode is executed by the target device to retrieve the corresponding oneof the plural data sets for the identified target device type. Theretrieved data set is then installed on the target device.

With reference to FIG. 4, there is provided a flowchart that outlines anexemplary process for creating and deploying a single installation fileto one or more target devices. At the startup (Step 60), the fileinstallation application (e.g., software 13 on development computer 12as depicted in FIG. 3), determines whether or not an installation file52 has already been created (Step 62). More specifically, initially thefile installation application comprises a base engine that is inintermediate language code and executable by any device that has ajust-in-time compiler. The base engine looks at the end of its file todetermine if there is any information (i.e., file sets or data sets)stored at the end of the executable. If there are data or file setsattached to the end of the executable (i.e., an installation file 52 hasalready been created), the application proceeds to Step 64; otherwise,the application proceeds to Step 68 to attached data/file sets to thebase engine.

In one approach, if an installation file 52 has not been created, theapplication prompts the user to enter data used to build theinstallation file 52 at Step 68. In another approach (not illustrated),the data used to build the installation file is obtained from a registryon the development platform. Data used to build the installation file 52can include information, such as, for example: which files are needed togo into the installation file; where to extract the files to when theyare installed; the dynamic root entry; and other information that willhelp to dynamically install the files on a given device. Becausedifferent devices can have different directory structures, the dynamicroot information allows for the same file to be extracted to differentpaths based on the type of device on which installation is beingperformed. The user entered data can also include information relatingto what to call the new installation file and the coding format of theinstallation file, explained in further detail below.

Once the application collects the input information from the user (Step70), the application proceeds to build an installation file 52 thatcomprises all of the required files and information needed to performextraction and installation at the target device(s) (Step 76). In oneapproach, the installation file 52 comprises a copy of the program 13used to collect the information from the developer with all of thepertinent files and extraction information attached to it. In oneapproach, the name and location of the installation file 52 ispreferably displayed on the development computer 12 (Step 78). After theinstallation file 52 is created and information regarding theinstallation file 52 is displayed, the final step comprises exiting theapplication (Step 80).

With reference to Step 62 in FIG. 4, once an installation file 52 hasbeen created (i.e., data plural data sets corresponding respectively toplural target device types are attached to the base engine), theapplication initiates installation mode. In a preferred approach,installation mode is initiated immediately after creation of theinstallation file. Installation mode typically comprises deploying theinstallation file 52 to one or more target devices. In one approach, theinstallation file 52 is automatically transferred to the targetdevice(s) to remotely initiate the installation process.

Once the installation file 52 has been deployed to a target device, thenext step is to just-in-time compile the engine portion of theinstallation file. The engine portion is transformed from intermediatelanguage code to code that is executable on the target device. Thetarget device executes the executable code to identify the target deviceas one of the plural target device types (step 64), to retrieve orextract the corresponding one of the plural data sets for the identifiedtarget device type (step 66), and to install the retrieved data set onthe target device.

With reference to the flowchart of FIG. 5, the method steps locatedabove line 25 are typically performed on a development platform 12,while the method steps located below line 25 are performed on one ormore target devices, such as devices 30, 32, 34, 36, 38, and 40.

In one exemplary approach, diagrammed in FIG. 5, the source code for thebase engine of the installation file is written in a .NET language, suchas, for example, C# (Step 82). In another approach (not shown), thesource code is written in Java or a similar suitable language. With therecent increase in languages that support just-in-time compilation, suchas, for example, .NET and Java, an application or program no longerneeds to be compiled for a specific type of processor. As a result, thesame program in uncompiled format can be installed and run on manydifferent types of devices.

With continued reference to FIG. 5, the source code of the base engineis compiled by a compiler (e.g., a .NET compiler) (Box 84) into anIntermediate Language Code (“IL code”) (Step 86). IL code comprises ageneric format that can later be compiled just-in-time at the targetdevice. The IL code does not contain any processor specificinstructions; rather, it has an .exe extension like any otherexecutable.

When the IL code of the engine is executed on the development platform12, the installation file is created (e.g., by concatenating theappropriate data sets to the IL engine). When the IL code is deployed tothe target device and executed, the IL code triggers the just-in-timecompiler (Box 88) to start up and compile the IL code into amachine-specific code that can then be executed by the target device.The machine-specific code typically does not generate a separate file;rather, in most cases the code is just-in-time compiled when a userwants to execute the program. As explained above, when the just-in-timecompiled machine specific code is executed by the target at Step 90, thetarget device performs a number of functions, such as extracting thedata set and installing the data set(s) appropriate for the targetdevice.

With reference once again to FIG. 4, the executable portion of theinstallation file 52 preferably runs a check to make sure no criticalerrors were encountered while extracting the files. Once theinstallation file 52 verifies that there are no critical errors andinstallation is complete, the next step is to determine whether or notto execute an autorun application (Step 72). The decision of whether ornot to autorun the application installed on the target device istypically determined by the user at Step 70, or by the default settingsor user preferences of the target device. In one embodiment, the targetdevice is configured to prompt the user to decide whether or not to runthe recently installed software. From Step 72, the next step is toeither autorun application (Step 74) or exit the application (Step 80).

While the exemplary process outlined in FIG. 4 has been illustrated anddescribed with particularity, it should be understood that no limitationof the scope of the invention is intended thereby. In one approach toinstalling software on multiple target devices with a singleinstallation file 52, one or more of the data sets within theinstallation file 52 are encrypted and/or compressed. In an alternativeapproach, the entire installation file, comprising both the engine andthe gathered plural data/file sets, is encrypted and/or compressed.Encrypted files are particularly useful where the file content issensitive. Here, a password would be required before the extractionprocess on the target device begins. Compressed files would help reducethe size of the installation file 52, which would in turn result inquicker transfer of the installation file to the target device(s).

In one variation to the data installation method described herein, theinstallation file 52 can be deleted from the target device whenextraction of the data/file sets is completed. In yet another variationto the data installation method described herein, at least one of thespecific files installed on the target device has a shortcut created toit after the data file(s) have been installed.

Having thus described a preferred embodiment of a system and method forinstalling software on multiple types of target devices with a singleinstallation file, it should be apparent to those skilled in the artthat certain advantages of the within system and method have beenachieved. It should also be appreciated that various modifications,adaptations, and alternative embodiments thereof may be made within thescope and spirit of the present invention. For example, a softwareinstallation system wherein the installation file source code iscompiled by a .Net compiler into an intermediate language code has beenillustrated, but it should be apparent that the inventive conceptsdescribed above would be equally applicable to a system wherein thesource code is compiled by a Java compiler. The invention is solelydefined by the following claims.

1. A method of installing data onto a target device, comprising thesteps of: providing an installation file, the installation filecomprising an engine concatenated with plural data sets, the plural datasets corresponding respectively to plural target device types havingdifferent directory structures, the engine being in an intermediatelanguage code; loading the installation file onto the target device;just-in-time compiling the engine into code executable on the targetdevice type; and executing the compiled engine to identify the targetdevice as one of the plural target device types, to retrieve thecorresponding one of the plural data sets for the identified targetdevice type, and to install the retrieved data set onto the targetdevice.
 2. The method of claim 1, wherein the step of providing theinstallation file comprises placing the installation file on a remotefile system that is accessible to the plural target device types,wherein the installation file can be downloaded onto the target devicetypes.
 3. The method of claim 2, wherein the step of placing theinstallation file on a remote file system comprises uploading theinstallation file to an internal network system.
 4. The method of claim2, wherein the step of placing the installation file on a remote filesystem comprises uploading the installation file to an internet site. 5.The method of claim 1, wherein the step of providing the installationfile comprises saving the installation file onto a storage medium anddistributing the storage medium to users of the plural target devicetypes.
 6. The method of claim 5, wherein the storage medium comprises acompact disc.
 7. A computer program product stored on a target device,comprising: an engine that is in an intermediate language format; andplural data sets corresponding respectively to plural target devicetypes having different directory structures, the plural data sets beingconcatenated with the engine; wherein the engine comprises computerexecutable instructions to be just-in-time compiled into code executableon a the target device; wherein the target device executable codecomprises instructions for: identifying the target device as one of theplural target device types; retrieving the corresponding one of theplural data sets for the identified target device type; and installingthe retrieved plural data set onto the target device.
 8. The product ofclaim 7, wherein the storage medium comprises a compact disc.
 9. Theproduct of claim 7, wherein: each data set is part of a data file; andthe product comprises plural data files corresponding respectively tothe plural target device types, the plural data sets being concatenatedwith the engine.